FIXES TO PRODUCTS ON THE -02 REVISION OF THE DCCONNECT CD
---------------------------------------------------------
  This file catalogs fixes made to the DCConnect products since we
  shipped the -02 revision of the DCConnect CD in June 1997.

  This file also explains how to install the fixes from the OS2FX-02.EXE
  self-extracting zip file.

  See the bottom of the file for the date of the last change.

  If you have the file OS2FX-02.EXE you can either create a diskette from
  which to install the fixes or you can expand the self-extracting zip file
  on the hard drive in any subdirectory and run the installation from that
  subdirectory.


IMPORTANT NOTE FOR WINDOWS NT USERS
-----------------------------------
  THIS FIX PACK HAS ONLY BEEN SET UP FOR OS/2 - WHICH AT THIS TIME IS THE
  PLATFORM FOR THE MAJORITY OF DCCONNECT INSTALLS.  A SEPTEMBER UPDATE IS
  PLANNED FOR THE DCCONNECT CD.  BECAUSE THAT UPDATE IS LESS THAN TWO MONTHS
  AWAY AND THERE ARE FEW NT INSTALLS AND THERE ARE NO KNOWN MAJOR BUGS AT THIS
  TIME, AN NT FIX PACK WILL NOT BE MADE AVAILABLE BEFORE THE -03 REVISION OF
  THE DCCONNECT CD BECOMES AVAILABLE.


IMPORTANT NOTE FOR ALL USERS:
-----------------------------
  These fixes can only be installed if your PC has been rebooted since you
  installed from the -02 revision of the DCConnect CD.  The installation makes
  use of some operating system environment variables (e.g. DCCONN).


EXPANDING AND INSTALLING OS/2 FIXES FROM THE HARD DRIVE
-------------------------------------------------------
  To expand and install OS2FX-02.EXE from somewhere on your hard drive,
  perform the following steps:

  1) Create or choose an empty directory anywhere on your harddrive.  For
     example: C:\TEMP

  2) Copy or download OS2FX-02.EXE to that directory

  3) Make sure that directory is the current directory and then run the
     executable by typing:

       OS2FX-02

     This will expand all the files into the current directory.

  4) To install the fixes, first make sure none of the DCConnect products are
     running and that the current directory is the one containing the expanded
     contents of the OS2FX-02 executable.  Issue the following command:

       INSTALL

  5) Continue with the section below marked: CHRONOLOGICAL SUMMARY OF
     FIXES/CHANGES


EXPANDING AND INSTALLING OS/2 FIXES USING DISKETTES
---------------------------------------------------
  The files in OS2FX-02.EXE self-extracting exectuable, cannot fit on a single
  diskette.  The necessary diskettes can be created using the command file,
  MAKEDSKS.CMD, which is part of OS2FX-02.EXE.  Perform the following steps:

  1) Create or choose an empty directory anywhere on your harddrive.  For
     example: C:\TEMP

  2) Copy or download OS2FX-02.EXE to that directory

  3) Make sure that directory is the current directory and then run the
     executable by entering:

       OS2FX-02

     This will expand all the files into the current directory.

  4) To create the diskettes, first get two completely blank, formatted 1.44
     3.5 in. diskettes.  Then run the following command file from the current
     directory:

       MAKEDSKS

     This will prompt you for each diskette and copy the appropriate files to
     each.

  5) To install the fixes contained on the fix diskettes, first make sure none
     of the DCConnect products are running and make sure the first fix
     diskette is in drive A:  Issue the following command:

       A:\INSTALL

     Additional diskettes will be prompted for as needed. (Of course drive B:
     could be used for installation as well).

   Once you have created the diskettes, you could also copy the contents of
   both to an empty directory on the target system and then run the
   installation from that directory.


CHRONOLOGICAL SUMMARY OF FIXES/CHANGES
--------------------------------------
6-11-97: Fixed possibility of trap when an attempt is made to delete an
  object that is linked to the mouse pointer.  The link is now cleared
  before the delete is performed.

6-17-97: The 'Options' option from the configuration pull-down menus now
  goes directly to the Options page of the Node notebook.  Likewise the
  'Program Binding' option of the terminal's mouse-button menu now goes
  directly to the bindings page of the terminal notebook.

6-17-97: Redid the left toolbar on the Function Group, Mailbox and CFR
  Configuration screens so that this toolbar no longer has to refresh
  when a terminal is added/deleted.  This also eliminated a source of a
  trap.  The only draw back is that the 'Real Terminals/Validation' icon
  will be shown even when no terminals or validation objects are defined.

6-17-97: Fixed possible trap in DCX.DLL if invalid data came back from a
  status call that is made during any of the API calls:
  DcxExectuteTermTransaction(), DcxSetTermUserVariable() or
  DcxSetNTermUserVariables().

6-17-97: Fixed mapping of 32-bit return code DCX_CMD_NOT_ALLOWED to 16-bit
  return code.  Was being mapped to DCC_DOWNLOAD_IN_PROGRESS - now changed
  to DCC_TRANSMIT_NAK.

6-18-97: Default names for functions groups should now always have the
  format FunctionGroupXX.

6-18-97: Fixed the Get Terminal User Variable function in TESTTERM.EXE so that
  it works properly when the current request returns no data or returns data
  that is shorter than that of the previous request.

6-20-97: Terminal (or any object) can no longer be deleted when its notebook
  is open.

6-20-97: Fixed trouble starting server when blanks in DCCONN path or current
  directory not .\BIN subdirectory.

6-20-97: Ability to clear message log added to the System Message Viewer.
  However, this can only be done when the server is running.

6-24-97: Tabbing in the notebooks has been improved - although you still
  can't tab to the pushbuttons.

6-24-97: Fixed major memory leaks that resulted when folders/configuration
  windows were closed or refreshed and when tool bars were refreshed.  This
  was the cause of many a trap that showed up when objects were deleted or
  added - or when windows were closed after objects were added/deleted.

6-25-97: Fixed problem with flyover text in Node notebook.

6-30-97: You can no longer drag a 'new CFR' object from the middle tool bar
  to the white space of the CFR Configuration window.  CFR objects are only
  created when the GUI is started - based on the actual .EXEs that exist in
  the \DCCONN\CFR directory.

7-02-97: Warning pop-up now given if date-time could not be set from the Node
  notebook.

7-02-97: GUI now ensures the current directory is the .\BIN subdirectory
  under the directory specified by the DCCONN environment variable.  This
  ensures the server starts up correctly.

7-03-97: In programs folder, if a program was currently linked to the mouse
  pointer and a Create Object was performed to create a new program, you would
  be prevented from changing the settings of the new program.  This has been
  fixed.

7-08-97: Fixed up the message text shown when HELP DCRxxxx is run from the
  command line.

7-08-97: Fixed cause of 50K memory leak every time a terminal notebook was
  opened.

7-08-97: Fixed rare trap during starup of GUI resulting from problem reading
  the validation directory.

7-08-97: Added ability for terminal in RF or TCP/IP environment to cause a
  failed download to be retried when the terminal is powered on or otherwise
  causes an I-am-here message to be sent to the DCConnect Server.
  Previously when a terminal was put into the Stopped state because it had
  failed too many downloads, the only way to get the terminal out of the
  Stopped state was by issuing another download to it.  Now when a terminal
  'I-am-here' message is received, if the terminal is in the Stopped state
  and a download is queued for it, the terminal will be changed to the
  'Load queued' state and the download should be started within the next
  30 seconds.

7-10-97: When a terminal of type X is assigned to a function group using
  type Y and the settings notebook is shown for the terminal, it will now
  be shown for type Y - that of the function group.  In addition, terminal
  of type X is unliked from that function group of type Y and then is
  assigned to a new function group containing no terminals, you will be
  prompted as to whether the new function group should assume type X or
  type Y.

7-14-97: When 'Data Monitor' is selected from a terminal's mouse-button
  menu, that terminal is now automatically added to the monitor's terminal
  window.

7-14-97: Fixed trap in Data Monitor when closing window after having
  dragged a terminal into the terminal window of the monitor.

7-15-97: Lots of fixes made in the validation file notebook.  Parameters
  are saved properly.  Order of precedence when files differ is: .TXT file,
  the DCVALDTN.DAT and finally .VAL file.  Mouse-button menu option 'Modify'
  now greyed out when validation object type is Phantom or Binary.

7-15-97: Fixed some year 2000 and year 2100 problems.

7-16-97: Pop-up now displayed when an invalid attempt is made to drop one
  object onto another object.  The pop-up explains why the drop cannot be
  performed.

7-16-97: If no path is specified for a validation objects source file.
  The GUI will automatically prepend the path \DCCONN\VAL - which is
  where the server assumes a file is located when a submit is performed
  and the source file has no path specified.

7-16-97: Fixed problem in GUI which caused downloads of 7526 terminals to
  fail if one or more system messages was blanked out.  In addition, the
  fact that the message was blanked out was not even preserved if you saved
  the configuration and then read it back in.  One fix took care of both
  problems.

7-18-97: (OS/2 only) Put in workaround for trap that occurs of more than one
  thread in a process makes API calls at the same time.  Had to do with one
  thread freeing up DAE resources that the other thread needed to use.
  With this workaround, we revert back to the original problem we were
  trying to fix which involves the need to shutdown any application that
  makes DCConnect API calls if the DCConnect Server has to be shut down
  and restarted.

  A fix to solve both problems should be available in the next CD.

7-18-97: (OS/2 only) Fixed minor problem in migration of SEND command in
  PGM16.CMD.  Any message referenced by this command had its reference count
  set incorrectly because the message number was being read improperly from
  the command string - off by 1.

----------------------------------------------------------------------------
End of fixes in version A: 8/97 for the -02 revision of the DCConnect CD
----------------------------------------------------------------------------